[00:00] In this lesson we'll learn about ignition redundancy. You can connect two gateways across the gateway network to create a redundant pair. One is designated as the master gateway where you'll manage all your settings and projects. The other is the backup gateway, which actively synchronizes with the master, creating a live copy of its entire configuration. You can learn how to set up redundancy in the next lesson in this course, but once it's in place, you can view the status of this relationship under the redundancy page. To get there, you would click on the platform tab and expand system, and then click redundancy. Right now we're viewing my master gateway as shown by the roll here towards the top of the screen. If the master were to fail or shut down, the backup gateway would assume control allowing our ignition system to continue running until the master is back online again. You can also force a failover by clicking on this button right here, and we'll go ahead and do so so we can see it in action.

[01:05] We'll confirm this message stating we may experience an interruption to the system and our display clients. Let's tab over to our backup gateway and we can see on the status page that this is now active as shown in our properties and the active uptime, all of the gateway settings that were on the master are still in place here, and all clients and sessions are now pointing to the backup. What we won't be able to do in the backup is make any gateway settings changes. For example, if we go to our gateway settings page and try to change something like the designer memory, we'll get this error stating We cannot modify settings on the backup node. There is a way to overwrite this behavior with backup versions, which we'll talk about more in the setting up redundancy lesson. Let's go back to the redundancy page and go over the rest of what's available to us here. If we scroll down, we'll see our list of redundancy providers. This view will be different depending on whether we are looking at the master or the backup.

[02:02] On the backup, we can see metrics for how long it takes to get updates from the provider and on the master, how long it takes for updates to be sent. If we scroll down more, we'll see all these system events giving us a timeline of when full sync events were requested. Finally, all the way at the bottom of this page, we'll see the log activity allowing us to enable debug and trace logs for a specific redundancy provider. You can also use this Merge the logs button to merge the logs here. With those on the main diagnostics log viewer in our diagnostics tab, let's go back to our master gateway to look at some features unique to that page. Earlier in this lesson, we forced the failover to the backup, and that button has now changed over to this assume control button. Clicking on this, we'll set the master as the active node, allowing all operations to continue here instead of on the backup. Finally, I wanna go over this force resync button. Clicking on this would perform a full synchronization of the system from the master gateway to the backup gateway. You would typically use it in specific troubleshooting scenarios where the automatic synchronization has failed or is not working as expected.